According to Ai 姨 (@ai_9684xtpa), both ZKJ and KOGE tokens experienced a severe flash crash tonight, which was orchestrated through a coordinated effort by three major addresses. These addresses targeted the unusually high trading volume and liquidity under the Binance Alpha context, executing large-scale liquidity withdrawals combined with continuous heavy selling. This dual pressure resulted in the sequential collapse of both ZKJ and KOGE tokens, with neither escaping the market impact. Traders are advised to closely monitor liquidity movements and large address activities, as such manipulative actions can lead to rapid price declines and increased volatility. Source: Twitter (@ai_9684xtpa, June 15, 2025).

According to Ai 姨 on Twitter, recent discussions around KOGE token highlight its low trading slippage but also underscore substantial risks, especially following the sharp decline on May 28. KOGE is not a stablecoin, and significant volatility can result in rapid losses for traders, as demonstrated using an 8200 USDT example. The future direction of KOGE remains uncertain, with questions about whether it will replicate KMNO's high spot trading volume or experience a major drawdown. Traders are advised to balance the potential advantages of low loss rates with the risk of sudden downturns, emphasizing the need for cautious position sizing and risk management (Source: @ai_9684xtpa on Twitter, June 7, 2025).

According to Ai 姨 (@ai_9684xtpa), KOGE token traders are experiencing higher-than-expected slippage, around 0.12%, due to automated routing across multiple liquidity pools. The inability to manually select the lowest-fee pool—such as the 0.04% pool—results in trades often being routed to pools with higher fees, particularly on platforms like Uniswap and PancakeSwap. Verified transaction tests confirm this increased cost. Traders should closely monitor pool selection and be aware that diverse liquidity pool structures can lead to elevated trading fees, impacting overall profitability in volatile markets (Source: @ai_9684xtpa, Twitter, June 6, 2025).